Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat(mysql): add GEOMETRY support #3069

Closed
wants to merge 3 commits into from
Closed

Conversation

mirromutth
Copy link

@mirromutth mirromutth commented Feb 21, 2024

Resolve #2735
Also may help to resolve issue in #166

Allows users enable geometry feature to use type geo_types::Geometry<f64> for GEOMETRY fields in MySQL.

Use ColumnType::Blob due to MySQL does not allow to execute prepared statement with a ColumnType::Geometry parameter, or am I missing something?

Based on geozero provided by georust

@mirromutth mirromutth force-pushed the main branch 2 times, most recently from 8095bba to 37c362f Compare February 22, 2024 03:29
@heksesang
Copy link

Any plans to merge this soon?

@abonander
Copy link
Collaborator

geozero provides integration with SQLx on their end so this would just introduce a dependency cycle.

I'm happy with it living there for the time being.

@abonander abonander closed this Aug 13, 2024
@gmli
Copy link

gmli commented Aug 28, 2024

Hi @abonander , if I understand correctly the documentation of geozero, Geometry for MySQL (with sqlx) isn’t supported on their side. Do you suggest to add this feature on the geozero project ?

@abonander
Copy link
Collaborator

Yes, since they've already added a sqlx feature. Otherwise it's just asking for annoying dependency cycle errors in Cargo.

@gmli
Copy link

gmli commented Aug 28, 2024

Thank you.
@mirromutth did you planned to do it on geozero ?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

MySQL Spatial Data Types
5 participants